failure 142:
Requirement failed: {setegid.05.02} error not met because its predicate (( priority_coverage == Priority_ReallyLow || ( priority_coverage == Priority_Unknown && setegid_spec == -1 ) ) && ( gid_coverage != Id_RealId && gid_coverage != Id_SavedSetId )) is false while error code EPERM is set ;
| location |
| trace |
/var/opt/lsb/test/olver-core/2013-01-21_10-20-40/process_meta_user_scenario.utz (process_meta_user_scenario.utt), line 37145 |
| occurence |
| scenario |
process_meta_user_scenario |
| specification function |
setegid_spec() |
| parameter value |
CallContext context = [pid=14702,thr=b75436c0] |
| parameter value |
GidT gid = 0 |
| parameter value |
ErrorCode * @errno = EOK |
| parameter value |
ErrorCode * errno = EPERM |
| return value |
(IntT) -1 |
coverage
& branch |
C
( Id, priority ) == ( Id_SavedSetId, Priority_Unknown ) |
| properties |
| REQ failed |
setegid.05.02 |
| kind |
POSTCONDITION_FAILED |
similar known bug(s)
|
The setegid() function sets the effective group ID of the calling process to the value,
specified as its argument.
According to LSB, if this argument equals to the real group ID or the saved set-group-ID,
or if the process has appropriate privileges, setegid() shall set the effective group ID
to this value.
But on the target machine setegid() fails when trying to set effective group ID to the
saved set-group-ID value.
Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102.
|
|